Power detection in the time domain on a periodic basis with statistical counters

ABSTRACT

Technology described herein can gather and statistically analyze time domain power data for enabling real-time adjustment of one or more parameters of a radio system. In an embodiment, a system can comprise a processor and a read circuit communicatively coupled to the processor, wherein the processor controls the read circuit to read power data in a time domain from a radio system, and an analysis component communicatively coupled to the processor, wherein the analysis component compares the power data in the time domain to a power threshold, and wherein, based on a result of the power data being compared to the power threshold, the analysis component sorts the power data into bins at a storage component communicatively coupled to the processor.

BACKGROUND

Modern cellular systems continue to advance, where dynamic changes canbe made to improve one or more aspects and/or to provide one or more newservices and/or other aspects. These dynamic changes can benefit fromknowledge, information and/or data regarding how a system isfunctioning, system issues, troubleshooting performance and/oradjustments made to address functions and/or issues. That is, suchknowledge, information and/or data relative to hardware, firmware and/orsoftware can be useful in proactively addressing such issues, performingtroubleshooting, and/or overall, improving one or more systems, and/orsubsystems of such cellular systems, such as of related radio systems.

SUMMARY

The following presents a simplified summary of the disclosed subjectmatter to provide a basic understanding of one or more of the variousembodiments described herein. This summary is not an extensive overviewof the various embodiments. It is intended neither to identify key orcritical elements of the various embodiments nor to delineate the scopeof the various embodiments. Its sole purpose is to present some conceptsof the disclosure in a streamlined form as a prelude to the moredetailed description that is presented later.

Generally provided is a system for time domain power detection. Timedomain detection can be performed on data at a radio system, such as atthe digital front end, where data is natively in the time domain.Ability to detect power in the time domain can enable the ability toprecisely extract power of a signal at a predetermined point, such as atap point, such as gated over a selected period of time. That power datacan be resolved to a degree for measuring radio performance. Timealignment of the data can enable input to output comparison (e.g.,relative to input/output of a respective digital front end), and/or canenable comparison at different points of an input chain and/or atdifferent points of an output chain.

An example method can comprise analyzing, by a system comprising aprocessor, at a system of a radio system, power data in a time domainthat is sorted according to a power threshold, storing, by the system,the power data in the time domain at a storage component, wherein thepower data in the time domain is stored into a group of bins based onthe sorting of the power data in the time domain, and counting, by thesystem, respective quantities of power data values at respective bins ofthe group of bins.

An example system can comprise a processor and a read circuitcommunicatively coupled to the processor, wherein the processor controlsthe read circuit to read power data in a time domain from a radiosystem, and an analysis component communicatively coupled to theprocessor, wherein the analysis component compares the power data in thetime domain to a power threshold, and wherein, based on a result of thepower data being compared to the power threshold, the analysis componentsorts the power data into bins at a storage component communicativelycoupled to the processor.

Another example system can comprise a group of power detectorsconfigured to detect collection of respective power data in a timedomain from a group of locations along an uplink path or a downlink pathof a radio system, wherein respective power detectors of the group ofpower detectors are configured to detect data relative to respectivedifferent time ranges of the time domain, wherein the system isconfigured to correlate the different time ranges of the time domain toone another, and wherein the power detectors of the group of powerdetectors comprise statistical counters that are configured toaccumulate respective counts of power data values at bins of a datastorage component.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology described herein is illustrated by way of example and notlimited in the accompanying figures, in which like reference numeralsindicate similar elements.

FIG. 1 illustrates a schematic representation of example elements of aradio system, in accordance with one or more embodiments and/orimplementations described herein.

FIG. 2 illustrates another schematic representation of the radio systemof FIG. 1 , comprising a radio data analysis system, in accordance withone or more embodiments and/or implementations described herein.

FIG. 3 illustrates a schematic diagram of the radio system of FIG. 1with the radio hardware unit signal capture portion expanded, inaccordance with one or more embodiments and/or implementations describedherein.

FIG. 4 illustrates a partial schematic diagram of a digital front enddownlink chain of the radio of the radio system of FIG. 1 , inaccordance with one or more embodiments and/or implementations describedherein.

FIG. 5 illustrates another partial schematic diagram of a digital frontend downlink chain of the radio of the radio system of FIG. 1 , inaccordance with one or more embodiments and/or implementations describedherein.

FIG. 6 illustrates a partial schematic diagram of a digital front enduplink chain of the radio of the radio system of FIG. 1 , in accordancewith one or more embodiments and/or implementations described herein.

FIG. 7 illustrates another partial schematic diagram of a digital frontend uplink chain of the radio of the radio system of FIG. 1 , inaccordance with one or more embodiments and/or implementations describedherein.

FIG. 8 illustrates a graph illustrating radio information at varioustime intervals, delineated periods of one symbol of time of a respectivetime domain, in accordance with one or more embodiments and/orimplementations described herein.

FIG. 9 illustrates a schematic representation of data being read,collected, and statistically analyzed over various time ranges, inparticular periods of one symbol of time, in accordance with one or moreembodiments and/or implementations described herein.

FIG. 10 illustrates a schematic diagram of a portion of the radiohardware unit of the radio system of FIG. 1 , in accordance with one ormore embodiments and/or implementations described herein.

FIG. 11 illustrates a process flow diagram of a method of reading,collecting, statistically analyzing, and storing time domain power dataof a radio system, in accordance with one or more embodiments and/orimplementations described herein.

FIG. 12 illustrates a block diagram of an example operating environmentinto which embodiments of the subject matter described herein can beincorporated.

FIG. 13 illustrates an example schematic block diagram of a computingenvironment with which the subject matter described herein can interactand/or be implemented at least in part, in accordance with one or moreembodiments and/or implementations described herein.

DETAILED DESCRIPTION Overview

The technology described herein is generally directed towards a processto collect, synchronize and/or analyze data, such as power data, in thetime domain of a radio system. The technology described herein canperform such operations in a hardware accelerated manner. That is, radiosystem reliability, serviceability and manageability are all aspects ofa functioning radio system of a cellular system that are important bothto the user and the provider. These aspects can benefit from knowledge,information and/or data/metadata gained from tracking, collecting,mapping and/or analyzing performance of a radio system. That is, thereis a benefit to measuring radio performance, and/or to generate and/orstore data in one or more ways that allow for comparative analysis ofsuch data (including metadata) that is collected from different sources,at different time points, and/or relative to one or more other dynamicand/or changing variables.

The data collected and/or statistically analyzed, and/or the results ofanalysis of the data can allow for real-time, immediate, short termand/or long term improvements, troubleshooting and/or predictivemodeling regarding radio system performance, failures, issues,continuity and/or other aspects. For example, the resulting “clean”and/or statistically accumulated data, such as telemetry, radiofrequency (e.g., analog data) and/or digital performance and/orcomparative data, and/or underlying infrastructure utilizationstatistics can be used to improve network performance, plan networkcapacity, and/or identify new service opportunities, relative to theradio system. Various types of data can be collected, such as, but notlimited to, data represented in a frequency domain (FD) and/or datarepresented in a time domain (TD). As used herein, “clean” can refer tonon-statistically analyzed data.

Generally, one or more embodiments described herein are directed todetection, statistical analysis, and storage of radio system power datain the time domain. The power data can be synchronized along systemtiming boundaries. Generally, the power data can be employed to provideproactive and reactive responses, updates and/or troubleshooting of arespective radio system of a cellular system. More particularly, one ormore embodiments here can facilitate an ability of a service provider(of a radio system) to precisely extract power of a signal at known andsynchronized period of time, and to resolve that data on a periodicbasis. In one or more embodiments, power data over various time ranges,from differing tap points of different sections and/or chains of a radiosystem can be measured, which power data can be used, as mentionedabove, relative to managing performance, system operation, maintenanceand customer experience of the respective radio system.

That is, in one or more embodiments, power detector data can beaccumulated (e.g., read and recorded, and selectively binned) on aperiodic basis over time, such as gathering power data of every symbolgoing into a respective power amplifier (PA). Simultaneously and/orsynchronously, power data can be gathered that is fed back from the PA.Additionally and/or alternatively, such power data can be looped to anuplink (UL) path and simultaneously and/or synchronously gathered.

Using the one or more embodiments described herein, such clean andstatistically analyzed data can not only be collected and measured, butalso recorded, stored and recalled, such as automatically and/oremploying artificial intelligence, machine learning, deep learningand/or the like to proactively and/or reactively address theperformance, system operation, maintenance and customer experience ofthe respective radio system.

To provide these one or more operations and/or features, referencethroughout this specification to “one embodiment,” “an embodiment,” “oneimplementation,” “an implementation,” etc. means that a particularfeature, structure, or characteristic described in connection with theembodiment/implementation can be included in at least oneembodiment/implementation. Thus, the appearances of such a phrase “inone embodiment,” “in an implementation,” etc. in various placesthroughout this specification are not necessarily all referring to thesame embodiment/implementation. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments/implementations.

As used herein, with respect to any aforementioned and below mentioneduses, the term “in response to” can refer to any one or more statesincluding, but not limited to: at the same time as, at least partiallyin parallel with, at least partially subsequent to and/or fullysubsequent to, where suitable.

As used herein, the term “entity” can refer to a machine, device, smartdevice, component, hardware, software and/or human.

As used herein, the term “cost” can refer to power, money, memory,processing power, thermal power, size, weight and/or the like.

As used herein, the term “resource” can refer to power, money, memory,processing power and/or the like.

Example Radio System Architectures

One or more embodiments are now described with reference to thedrawings, where like referenced numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth to provide a morethorough understanding of the one or more embodiments. It is evident,however, in various cases, that the one or more embodiments can bepracticed without these specific details.

Further, the embodiments depicted in one or more figures describedherein are for illustration only, and as such, the architecture ofembodiments is not limited to the systems, devices and/or componentsdepicted therein, nor to any particular order, connection and/orcoupling of systems, devices and/or components depicted therein. Forexample, in one or more embodiments, the non-limiting systemarchitecture 100 as illustrated at FIG. 1 , and/or systems thereof, canfurther comprise one or more computer and/or computing-based elementsdescribed herein with reference to an operating environment, such as theoperating environment 1200 illustrated at FIG. 12 . In one or moredescribed embodiments, computer and/or computing-based elements can beused in connection with implementing one or more of the systems,devices, components and/or computer-implemented operations shown and/ordescribed in connection with FIG. 1 and/or with other figures describedherein.

Turning now to FIG. 1 , a high-level radio system architecture isillustrated at 100. The radio system 100 can comprise a distributed unit(DU) signal injection portion 104 (also herein referred to as a DUportion 104) and a radio unit (RU) 101. The RU 101 can comprise a radiounit (RU) signal injection portion 106 (also herein referred to as an RUsignal injection portion 106), the radio control 108, and an RU signalcapture portion 110. Generally, the DU portion 104 can provide bothbaseband processing and RF functions. The RU signal capture portion 110can take signals from a respective antenna 120 and convert the RF signalinto a data signal, and vice versa. The RU signal capture portion 110can have one or more statistical counters, accumulators, countercircuits and/or the like.

In one or more embodiments, the RU signal capture portion 110 cananalyze data captured, such as via historical information. This analysisand data gathering can be performed at least partially autonomously,such as majoratively and/or fully autonomously, such as absent inputfrom the DU portion 104 and/or any centralized unit (CU). In one or moreembodiments, the radio control 108, in view of information received fromthe RU signal capture portion 110, can place an order for service,maintenance, hardware and/or firmware to a core data center 112. In oneor more embodiments, the radio control 108, in view of informationreceived from the RU signal capture portion 110, can at least partiallyautonomously request or request and receive one or more software,firmware and/or other system updates. Together, the DU portion 104 andRU portion 106 can provide data to, and receive data from, the coredatacenter 112.

Turning next to FIG. 2 , an example of a radio data analysis systemarchitecture is illustrated at 200, with description being providedbelow. The radio data analysis system 200 can be part of the radiosystem 100 (e.g., of FIG. 1 ) or can be at least partially external tothe radio system 100. For purposes of brevity, additional aspects of theradio system 100 (e.g., as illustrated at FIG. 1 ) are not illustratedat FIG. 2 . While referring here to one or more processes, operations,facilitations and/or uses of the non-limiting system architecture 200,description provided herein, both above and below, also can be relevantto one or more other non-limiting system architectures described herein.

FIG. 2 illustrates a schematic of the radio data analysis system 200 fordetecting, reading and gathering power data in the time domain relativeto one or more known periods of time, which can be aligned to oneanother, such as relative to time boundaries of the radio system 100.Generally, the power data in the time domain can be read and collectedat various tap points of the radio system 100, where the power data isnatively in the time domain.

Generally, the radio data analysis system 200 can comprise any suitablecomputing devices, hardware, software, operating systems, drivers,network interfaces and/or so forth. However, for purposes of brevity,only components generally relevant to time domain power data detection,collection and/or analysis are illustrated in FIG. 2 . For example, theradio data analysis system 200 can comprise a processor 207, memory 209,time domain power detector 210, read circuit 211, delaying circuit 218,measurement circuit 214, analysis component 218 and/oraccumulator/counter circuit 220.

Discussion first turns to the processor 207, memory 209 and bus 205 ofthe radio data analysis system 200.

In one or more embodiments, radio data analysis system 200 can comprisethe processor 207 (e.g., computer processing unit, microprocessor,classical processor and/or like processor). In one or more embodiments,a component associated with radio data analysis system 200, as describedherein with or without reference to the one or more figures of the oneor more embodiments, can comprise one or more computer and/or machinereadable, writable and/or executable components and/or instructions thatcan be executed by processor 207 to facilitate performance of one ormore processes defined by such component(s) and/or instruction(s). Inone or more embodiments, the processor 207 can comprise the measurementcircuit 214, delaying circuit 218, analysis component 218 and/oraccumulator/counter circuit 220.

The processor 207 can be configured to control one or morecomponents/elements of the radio data analysis system 200, such as thepower detector 210, read circuit 211, delaying circuit 218, measurementcircuit 214, analysis component 218 and/or accumulator/counter circuit220. That is, the processor 207 can be configured to control collectionof power data relative to the radio system 100.

It is noted that the radio system 100 comprises a plurality ofsubcarriers 250, and that data collected in the time domain is generallycollected relative to such subcarriers 250, in the sense that power datain the time domain over a range of time can is data relative to thevarious subcarriers of a range (e.g., symbol of 1 period) of that time.In one or more embodiments, the radio system 100 can have subcarrierspacing such as 30 KHz spacing or numerology 1 spacing.

As used herein, a subcarrier is a sideband of a radio frequency carrierwave, which can be modulated. An operating radio system, such as theradio system 100, can have a plurality of subcarriers, such assubcarriers 250 numbered from 0, 1, 2 . . . to j. Subcarrier spacing atthe radio system 100 can be based on the numerology configuration of thesystem.

Additionally, generally at a radio system, the more subcarriers that canbe packed into a frequency range (i.e., the narrow subcarrier spacingused), the more data that can be transmitted and/or received. In oneexample, the radio system 100 can have subcarrier spacing of about 30KHz or numerology 1. Based on physics (e.g., anti-proportionalrelationship between subcarrier spacing and orthogonal frequencydivision multiplexing—OFDM—symbol length), narrow subcarrier spacing cancorrespond to longer OFDM symbol length. Longer OFDM symbol length cancorrespond to additional spacing for CP (cyclic prefix). With longer CP,the signal can be more tolerable to a fading channel.

The processor 207 can be configured to control collection of power datain the time domain at various resolutions and aver various known periodsof time. The known periods/ranges of time can be synchronized to oneanother via one or more time-alignment operations, time stamps and/orthe like, such as by the processor 207.

For example, in one or more embodiments, sampling resolution can bedetermined by a highest sampling rate and/or number of samples collected(the period), such as at least 16 samples. Sampling rates can varydepending on which block of a DFE chain is being tapped for datadetected. Internal blocks of a DFE can run as high as 491.52 Msps, orhigher, with a poly-phase configuration with a bit width of 16 bit forboth I and Q. Parallel paths shall be supported simultaneously.

In one or more embodiments, a time range over which power data can bedetected can be a period of a symbol, sub-period of a symbol, ormultiple symbol periods, for example. An exemplary case of sub-symbolperiod can be under a condition where a glitch or switching boundary canresult in undesired signal corruption where detailed analysis at asub-period granularity can be desired.

In one or more embodiments, a time range over which power data can bedefined by a gateable event, such as relative to one or more operationsperformed by one or more blocks of a DFE chain, such as the DFE chain304 (FIG. 3 ), UL chain 600 (FIGS. 6 and 7 ) and/or DL chain 400 (FIGS.4 and 5 ).

In one or more embodiments, the radio data analysis system 200 cancomprise the machine-readable memory 209 that can be operably connectedto the processor 207. The memory 209 can store computer-executableinstructions that, upon execution by the processor 207, can cause theprocessor 207 and/or one or more other components of the radio dataanalysis system 200 (e.g., power detector 210, read circuit 211,delaying circuit 218, measurement circuit 214, analysis component 218and/or accumulator/counter circuit 220) to perform one or more actions.In one or more embodiments, the memory 209 can store one or morecomputer-executable components.

Radio data analysis system 200 and/or a component thereof as describedherein, can be communicatively, electrically, operatively, opticallyand/or otherwise coupled to one another via a bus 205 to performfunctions of non-limiting system architecture 200, radio data analysissystem 200 and/or one or more components thereof and/or coupledtherewith. Bus 205 can comprise one or more of a memory bus, memorycontroller, peripheral bus, external bus, local bus and/or another typeof bus that can employ one or more bus architectures. One or more ofthese examples of bus 205 can be employed to implement one or moreembodiments described herein.

In one or more embodiments, radio data analysis system 200 can becoupled (e.g., communicatively, electrically, operatively, opticallyand/or like function) to one or more external systems (e.g., a systemmanagement application), sources and/or devices (e.g., classicalcommunication devices and/or like devices), such as via a network. Inone or more embodiments, one or more of the components of thenon-limiting system architecture 200 can reside in the cloud, and/or canreside locally in a local computing environment (e.g., at a specifiedlocation(s)).

In addition to the processor 207 and/or memory 209 described above,radio data analysis system 200 can comprise one or more computer and/ormachine readable, writable and/or executable components and/orinstructions that, when executed by processor 207, can facilitateperformance of one or more operations defined by such component(s)and/or instruction(s).

Turning now to additional elements of the radio data analysis system200, time domain (TD) power detection can be performed on data within adata stream of a digital front end (DFE) of a radio system, where suchdata is natively in time domain. Ability to detect power in the timedomain can allow for the ability to precisely extract the power of asignal at a period, multiple period or sub-period time range, forexample. Power detection can be implemented at a location coupled to,but spaced from, such as coupled near, an input to the radio system,such as at various tap points spaced along (e.g., between) a DFE'svarious blocks (e.g., of an uplink chain or a downlink chain). Timealignment of this data can enable input to output data comparison, inputto input comparison and/or output to output comparison.

Turning first to the power detector 210, which can be a time domain (TD)power detector, while the TD PD 210 is shown as part of the radio dataanalysis system 200 the power detector 210 can be additionally and/oralternatively part of the RU signal capture portion 110.

Power detectors are RF components that can convert an RF input signalinto an output voltage and/or a digital and/or digitized representationthereof that can be proportional to the incident RF power. Powerdetectors can be employed for operations relative to automatic gaincontrol circuits, transmit antenna power monitoring, and/or protectingsensitive circuits from pulses and/or power spikes.

The power detector 210 can be any suitable power detector, such asconventionally known by those having skill in the art. In one or moreembodiments, the power detector 210 can be capable of reading timedomain power data. In one or more embodiments, the power detector 210can be configured to read and/or detect RMS power/current data and/orpeak power/current data. That is, the power detector 210 can be both RMSand peak, temporally and/or over frequency.

The power detector 210 can be coupled to a digital front end (DFB)uplink (UL) or downlink (DL) chain, such as of the radio 107, foraccessing the time domain representation of a plurality of subcarriers250 of the radio 107. For example, as illustrated at FIGS. 4 to 7 , thepower detector representation 709 can be comprised by and/or separatefrom the power detectors 210. It is appreciated that power detectors 210and 709 can be interchangeable. Also at FIGS. 4 to 7 , the powerdetector representation 709 can stem from various power detector tappoints, including 410 and 610, but also including various otherunlabeled tap points TP of the DL chain 400 (FIGS. 4 and 5 ) and/or ULchain 600 (FIGS. 6 and 7 ).

These schematics of FIGS. 4 to 7 show an additional layer of detail ascompared to the schematic illustration of FIG. 3 . It is noted that theDL chain 400 and UL chain 600 have are separately shown, and also aresplit into portions for purposes of detailed illustration. For example,DL chain portions 400 a and 400 b and UL chain portions 600 a and 600 bare coupled to one another at least at connection points 402, 404, 406,408, 502, 602, 604 and 606.

The power detector 210 can comprise a read circuit 211. The read circuit211 can be communicatively coupled to the processor 207 and can be atleast partially controlled by the processor 207 to read, at the radiosystem 100, such as at UL chain 600, DL chain 400, and/or at othervarious tap points at the radio system 100, power data in a time domain.This power data can be native power data at UL chain 600 m DL chain 400and/or at other various tap points at the radio system 100.

As illustrated at FIG. 3 , one or more power detectors 210, and thusalso respective read circuits 211, can read data from a temporal TD datastream 302. The power detectors 210 can read power data across at leasta portion of a downlink chain or uplink chain of the DFE (e.g., a DFEchain 304). The power detectors 210 can read such power data along aselected time range that can be defined by a specified upper limit oftime and a specified power limit of time of the radio system 100, whichcan be aligned at time boundaries of the radio systems, such as symbols.For example, the read circuit 211 can read power data at a definedgranularity based on a period of one symbol of time of the time domain.In one or more embodiments, the granularity can be that of a selectedsampling rate, such as 491.52 Msps. The power detectors 210 can beconfigured to employ one or more databases, such as a waveform/resourceblock (RB)/resource element (RE) databases 308 to therefore detect,recognize and/or convert data from the temporal TD data stream 302 topower data in the time domain.

The power data can be read by the read circuit 211/power detector 210 atvarious locations of such a power detector 210, such as illustrated atvarious tap points (TP) at FIGS. 4 to 7 , such as tap point 410 (FIG. 4) and tap point 610 (FIG. 6 ). It is noted that conventional radiosystem DFE chains do not comprise resources for transferring data withinthe DFE at an accelerated rate. Here, generally, the radio system 100can haul TD data using unused resources in one or more DFE, UL and/or DLchains, for example. In one or more embodiments, the radio system 100can forward, e.g., by the processor 107 and/or power detectors 210, timedomain power data from separate tap points to a logical collectionand/or storage point in the DFE chain (e.g., storage 414 and/or 702) bysharing the existing uplink (UL) DFE paths for different branches duringa downlink (DL) time domain duplexing (TDD) period. Put another way, theread circuit 211 can be configured to transmit the power data in thetime domain along a chain of the radio system 100 other than the chainat which the tap point/power detector is positioned/located/operating.In one or more embodiments, such “hauling” or “forwarding” of timedomain data can comprise transforming time domain data to frequencydomain data on/at a respective UL enhanced common public radio interface(eCPRI) link. For example, looking to FIGS. 4 to 7 , data from varioustap points (TP) can be forwarded between tap points, such as from the DLchain 400 to the UL chain 600. See, for example, the path at FIGS. 5 and6 connected by connector 502. Forwarding can be operated over suchrepresentative paths.

UL data paths can be reverted back to normal live-air operation duringTDD UL period. TDD can have a transmit Tx_ON state, where the transmitis ON, and a receive Rx_ON state where the transmit is OFF, and thesestates can be mutually exclusive. In one or more embodiments, TD datacan be frequency shifted (DDC or DUC), filtered (FIR, HB), and/ordecimated (/x) to select a sub-band, or lessen the amount of datacollected as a requirement. An alternative desirable data processingoption can be to sub-band (filter) the TD data.

In one or more embodiments, a read circuit 211 can perform one or morecalculations directed to determining the power data in the time domainfrom information, signals and/or the like detected by the power detector210.

As noted above, TD power data can be gathered based on RMS current orpeak current specifications. As such, the power detectors 210 can beconfigured for RMS power and/or peak power applications.

In one or more embodiments, a read circuit 211 of the respective readcircuits 211, can be configured to identify and/or to separately recordpeaks of power data that exceed one or more selected power data unitthresholds in the time domain. For example, this identification can beperformed prior to initial storage and/or after initial storage. This“pre-conditioning” of data can allow for rapid analysis of bulk data,such as in a relatively real time fashion and/or at any other subsequentpoint in time, to thereby determine one or more current and/orhistorical characteristics of the radio system 100, such as radio system100 operation, relative to the TD power data.

One or more actions can be taken relative to the preconditioned data toassist with radio system frequency, maintenance, customer experienceand/or the like. In one or more embodiments, one or more actions can betriggered, such as by a respective ready circuit, such as relative to aquantity, quality and/or other aspect of the data read, collected and/orstored.

In one or more embodiments, a read circuit 211 can adjust a samplingrate of the power data in the time domain, such as of one or moreparticular power detectors 210, such as based on feedback from theprocessor 207, radio system CU and/or control datacenter 112.

In one or more embodiments, one or more gathered/read sets of power datacan be time aligned relative to one or more other gathered/read sets ofpower data (e.g., data from UL chain 600 vs data from DL chain 400). Forexample, as shown at FIGS. 4 to 7 , time alignment can be performed onthe collected data, such as relative to 430 (FIG. 4 ) and/or 630 (FIG. 7). For example, blocks 430 and 630 can be blocks that collectinformation for time alignment (e.g., gating and/or markers) that cansubsequently be used to accelerate processing of the data. For example,one or more blocks 430 and/or 630 can comprise, be communicativelycoupled to and/or represent a measurement circuit 214 and/or a delayingcircuit 218, as described below. It will be appreciated that such timealignment can be performed during power data collection, before initialpower data storage and/or after power data is initially stored.

A measurement circuit 214 can be communicatively coupled to theprocessor 207 and can measure a selected time range along a definedportion of a DFE chain, such as a downlink chain (e.g., 400) or uplinkchain (e.g., 600) of the radio system 100. Measurement data from themeasurement circuit 214 can be correlated to the stored power dataand/or to other measured data by the measurement circuit 214. Forexample, synchronizing resulting from the measurement data can beprovided by one or more time stamps that can be stored with the powerdata and/or referenced to the power data. For example, various tappoints (e.g., 410, 610) can be disposed between functional circuitelements of the downlink or uplink chains 400, 600, and signal timedelay across the functional circuit elements can measured by themeasurement circuit and stored to the collected power data by the groupof power detectors 210.

Additionally and/or alternatively, a delaying circuit 218 can becommunicatively coupled to the processor 207, which delaying circuit 218can delay a second set of power data in the time domain to therebyadjust a selected time range of the second set of power data to aselected time range of the first power data. For example, in one or moreembodiments, the delaying circuit 218, such as in cooperation with themeasurement circuit 214, can start, stop and/or pause collection ofpower data in the time domain at one or more time/event boundaries, suchas to facilitate the delay. In such cases, one or more read circuits 211can synchronously read the adjusted second set of power data and thefirst set of power data. The delaying circuit 218 can define an adjustedtime range stamp comprising a measured adjustment in the time range ofthe second set of data, thus allowing for referencing of a correlationbetween the selected time range and the adjusted second time range tothe power data.

Indeed, relative to the power detectors 210, read circuits 211,measurement circuit 214 and delaying circuit 218, the TD power data canbe detected within a known time boundary over which respectivemeasurement conditions are known and understood. In this way, capturingdata across these time boundaries, and thus provision of an undeterminedset of information, from one or more different symbols, can be avoided,unless particularly intentioned. Instead, synchronization of TD powerdata, such as between UL and DL chains, and/or between/among variouslocations along the UL and DL chains, can be performed and/or otherwiseprovided. Also, indeed, such symbol/symbol alignment can ensure that thepower data being compared/contrasted captured from different tap pointscan produce relevant and comparable results. Such comparison can bebetween UL and DL data and/or between data at different historicalpoints in time.

In one or more embodiments, time alignment can be provided down to theclock level (e.g., via sampling bins). For example, if the clock is491.52 Msps, the data captured at diverse tapping points can besynchronized to the system clock and ‘clocked’ on the proper clockedges. Time alignment of time-domain frequency converted data (passingthrough a DDC or DUC, or decimated data) can be maintained even if whenit is transformed into different sampling regimes. When contrasting datastreams from disparate locations in the DFE, it can be beneficial toalign to the same clock edge for ease of processing. For example, sinceall of a system's clocks are maintained and/or derived from a commonclock reference, then all time regimes can be based from a central clocksource and time alignment of such time regimes therefore can bereferenceable and lockable to one another via multiples of the sourceclock frequency.

Discussion now turns to statistical accumulation (e.g., statisticalanalysis of the TD power data and storage thereof) by the radio dataanalysis system 200.

The analysis component 218 can be communicatively coupled to theprocessor 207 and can be configured to compare the power data in thetime domain to a power threshold, such as a current threshold. Suchpower threshold can be a root-mean-square (RMS) threshold or a peakvalue threshold. Based on a result of the power data being compared tothe power threshold, the analysis component 218 can thus sort the powerdata into bins at a storage component communicatively coupled to and/oraccessible to the processor 207. That is, the power threshold can beapplied to separate the power data into root-mean-square or a peakvalues.

An advantage of the threshold counters can be to measure long termtraffic load distribution by “binning” as shown in a typical Histogram,based on the settable threshold or thresholds. The result of the RMS andpeak power detector measurements over a temporal period can then bestored in a suitable storage medium. It is noted that binning may be ofa dimension covering many power ranges.

For purposes of illustration, turning again to FIG. 3 , one or morethresholds 314 can be applied by the analysis component 218 to therebysort power data in the time domain into various bins, such as upperthreshold bin 316 and lower threshold bin 318. Indeed, as illustrated atFIG. 9 , additional bins 910 can be employed, such as employingdifferent bins for different thresholds 914 and/or threshold types. Thiscan include different RMS thresholds, different peak thresholds,different thresholds for different subcarriers 250, for different groupsof subcarriers 250, and/or for any combination thereof.

For example, if a power detector measurement is above the prescribed orprogramed threshold a “RMS_UpperCounter” can incremented. If themeasurement is below the threshold a “RMS_LowerCounter” can beincremented.

For another example, if a power detector measurement is above theprescribed or programed threshold a “Peak_UpperCounter” can beincremented. If the measurement is below the programed threshold a“Peak_LowerCounter” can be incremented.

Furthermore, in one or more embodiments, such bins 910 (FIG. 9 ) can betemporary wherein the accumulator circuit or the counter circuit 220 canbe configured to generate an interrupt signal triggering a copying ortransferring of the power data from one or more of the bins 910 to oneor more other bins, such as long-term storage bins or historicalanalysis bins. That is, put another way, an exemplary result of aninterrupt may be to trigger a capture or data dump to more permanentmemories or flight recorder.

Additionally, in one or more embodiments, the analysis component 218 canbe configured to compare the power data in the time domain prior tostored power data in the time domain at a suitable storage component,such as the bins 910, memory 209, storage 702, storage 414 and/or thelike. For example, based on the known time ranges of the data, and thussuch datas being time aligned relative to one another, one or morecurrent datas can be compared to one or more historical datas, such asautomatically, and/or such as with respect to one or more gateableevents. One or more thresholds can be employed for such comparison, withone or more triggers being initiated, such as by the analysis component218, in response to one or more of such thresholds being met and/orexceeded. These operations can allow for automatic “pre-conditioning” ofstatistical data based on previously gathered data, which“pre-conditioned” data can be used in real time and/or at any subsequenttime thereafter. In one or more embodiments, analysis of statisticaldata captured can be employed to generate, such as by the analysiscomponent 218, a histogram distribution of power data detected. That is,data can be analyzed over time to determine radio system performance orbeneficial system performance modifications.

It is noted that in one or more embodiments, time domain power dataprior to any analysis operations (e.g., “pre-conditioning” operations”)also can be stored, such as separately from analyzed data. This “clean”data can be stored at any suitable storage component, such as the bins910, memory 209, storage 702, storage 414 and/or the like. This “clean”data can be used in connection with and/or separately from the“pre-conditioned” data. The “clean” data can be recalled at any suitabletime for analysis and/or other use.

Next, an accumulator or counter circuit 220 can be communicativelycoupled to the processor 207 and can be configured to record power dataquantities stored at one or more of the bins at the suitable storagecomponent. That is, TD power detector data can pass through a thresholdfilter where the output can further be counted and the count accumulatedin an accumulator for ease of statistical analysis over time. It isnoted that the TD power detector data can be assessed by the accumulatoror counter circuit 200 before being binned and/or after being binned,such as where the data is recalled to the accumulator or counter circuit200 after being binned.

Different counter circuits 200 can be employed for different subcarriersand/or for different analysis components 218. Thus, different analysiscomponents 218 can be employed for different subcarriers and/or powerdetectors, where suitable.

Counter width can be dimensioned to capture sufficient information(e.g., a selected quantity) on performance parameters. For example, 15minute intervals/histograms at 60 kHz subcarrier spacing (SCs) can be anexemplary temporal setting. Counter circuits 200 can be gateable insynchronization with radio system timing and states. An exemplary casecan be Tx_ON/Rx_ON states, where Tx refers to “transmit” and Rx refersto “receive”.

In one or more embodiments, the aforementioned “clean” time domain powerdata likewise can be submitted, transmitted and/or otherwise sent to theaccumulator or counter circuit 200 prior to and/or after initialstorage. For example, mere quantity of “clean” data can be “counted”and/or otherwise tracked. Storage of such counted “clean” data can beseparate any of the aforementioned datas.

In one or more embodiments, threshold measurements can also be used formeasuring occurrence of extreme conditions or “spikes” in the power datadetected. In one or more embodiments, the analysis component 218 and/orthe counter circuit 200 can generate an interrupt or flag based onmeeting and/or exceeding one or more of the sorting thresholds or basedon one or more separate interrupt thresholds. In an exemplary case,detection can involve triggering a system event that affects systemperformance. In one or more embodiments, a trigger may not be generatedby the analysis component 218 and/or the counter circuit 200 until aselected quantity of threshold interrupt events are statisticallycounted.

In one or more embodiments, a determination of low RMS and high peakscan trigger a decision to a radio controller of a respective radiosystem to clip a signal to improve efficiency. In one or moreembodiments, a determination of blocker level before a filter an enableUL filter optimization.

In one or more embodiments, the analysis component 218 can enhanceaccuracy of the power data in the time domain that is detected by usinginformation from the C-plane of the radio system (e.g., FIG. 7 ). In oneor more embodiments, information from the C-Plane can be employed toaccumulate data in a more precise fashion. For example, operation boostand reduction of power can not be considered for Tx-blanking info andtherefore can be a possible source of error in power detection ortraffic estimation applications. For another example, such data from theC-plane can be employed to further enhance the accuracy of powerdetected associated with data for reduced resource block (RB) count,which power can be not necessarily reduced due to boost.

Again referring FIGS. 4 to 7 , and also FIG. 2 ,collected/read/gathered/statistically analyzed/clean data can be stored.As indicated above, one or more calculations and/or analysis can beperformed during collection, prior to initial storage and/or afterinitial storage. Storage employed can be configured for recall of datafor subsequent use and/or analysis. For example, the power data can bestored at a memory (e.g., memory 209) communicatively coupled to theprocessor 207 and configured to receive and store the power data in thetime domain from the read circuit 211. The memory and/or other storagecan initially be short-term memory, and thus a long-term memory 230 canbe employed to which power data can be moved from the temporary orshort-term memory. The long-term memory can be configured to store datalonger than the temporary or short-term memory.

Referring briefly to FIG. 8 and the graph 800, in one or moreembodiments of the radio system 100, TD power data can beread/gathered/collected at defined time ranges along the time domain.Such time domain data 802, as illustrated can be an alternative tofrequency domain power data. Indeed, such time domain data 802 is notindicated relative to one or more subcarriers, but rather relative to arange of time, such as a portion of one or more symbols of time, in thecontext of 5G cellular, for example. Although, other intervals can beemployed to define periods of time in a time domain.

For further illustration, turning to FIG. 9 and the schematic 900,various TD data, e.g., from the power detectors at tap points 410 and610, can be gathered relative to various time intervals, such asperiods, such as aligned at symbols of time. In one or more embodiments,all symbols of time of a respective time domain can be read, collected,gathered and/or analyzed by the radio data analysis system 200.

Referring next to FIG. 10 , detail is provided relative to a TD powerdetector 1012 at a tap point 1010. The TD power detector 1012 can besimilar to the TD power detectors 210 discussed above, and thusdiscussion related to the TD power detectors 210 can equally apply tothe TD power detector 1012 and/or vice versa. It is noted that any oneof the aforedescribed tap points 410, 610 and/or TP, at which a powerdetector 210 can be located and/or coupled, can be replaced by the tappoint 1010 and power detector 1012.

As illustrated, one or more operations can be performed, such as by thepower detector 1012 and/or a by a respective processor. The one or moreoperations can comprise (and/or be employed for) time domain sampling, afrequency mask, buffering, CP removal, applying a frequency domain mask,fault and flag analysis for interrupt instantaneous peak, powermonitoring, analysis and fault detection, radio optimization control andactuation, and/or the like. One or more of the operations can beperformed prior to or via recall from storage 1014. It is noted thatstorage 1014 can be replaced by and/or supplemented by any of memory209, storage 414, storage 702 and/or other storage of the radio system100 and/or external thereto.

Referring now again to FIG. 2 , in one or more embodiments, a group ofTD power detectors 210, as illustrated at FIG. 2 , can be collectivelyconfigured to control collection of TD power data from various tappoints (e.g., 410, 610, TP) of radio system 100. The power detectors 210of the group of power detectors can comprise respective read circuits211 that can be configured to read the power data in a time domain, ofalong time ranges that can be defined relative to time boundaries of theradio system 100. The respective read circuits 211 can be furtherconfigured to read the power data in the time domain to a memory (e.g.,memory 209 or other storage) communicatively coupled to and configuredto receive and store power data. One or more measurement circuits 214and/or delaying circuits 218 can perform one or more measurements,stampings and/or calculations to synchronize and/or correlate TD powerdata read at one TP from TD power data read at another TP.

The power detectors 210 of the group of power detectors can comprisestatistical counters 200 that can be configured to receive therespective time domain power data having been sorted according to apower threshold, such as by the analysis component 218. In one or moreembodiments, the statistical counters can be configured to accumulaterespective counts of power data values at bins of a group of suitabledata storage components. For example, a first number of the statisticalcounters can be set relative to a second number of the bins to result inthe system 200 comprising at least one statistical counter per bin ofthe data storage component.

In one or more embodiments, a group of radio data analysis systems 200can be provided at a radio system (e.g., radio system 100). Each radiodata analysis system 200 of the group of systems can be configured toread and record power data in the time domain along respective differentselected time ranges that each can be aligned at the radio system's(e.g., radio system 100) time boundaries.

In one or more embodiments, any of the aforementioned detecting,reading, measuring and/or delaying can be implemented at plural radioantenna branches of a same radio system, a different radio system, orrelative to two or more carriers employing at least the radio system. Inan exemplary case a radio data analysis system 200 can record power datafor one, some, or all antenna branches, such as simultaneously.

In one or more embodiments, the radio data analysis system 200, such asthe processor 207, can combine, such as at the memory 209 and/or otherstorage first power data in the time domain with second power data in afrequency domain of the same radio system 100, wherein the frequencydomain can comprise data from one or more subcarriers from one or moretime ranges (e.g., periods of time) of the radio system 100. In anexemplary case, signals when combined with TD (time domain) power detectand/or combined with open radio access network (ORAN) blocks and/ortransmit (Tx) blanking information can enable aspects of determinationof performance aspects of the radio system 100 not limited to systemoperations and/or maintenance.

Turning now to FIG. 11 , a process flow comprising a set of operationsis illustrated relative to FIG. 2 for detecting, statisticallyanalyzing, and/or storing time-aligned time domain power data, such aswhere the power data is natively in the time domain. One or moreelements, objects and/or components referenced in the process flow 1100can be those of system 100 and/or system 200. Repetitive description oflike elements and/or processes employed in respective embodiments isomitted for sake of brevity.

At operation 1102, the process flow 1100 can comprise reading, by thesystem (e.g., read circuit 211), power data in a time domain from aradio system.

At operation 1106, the process flow 1100 can comprise comparing, by thesystem (e.g., analysis component 218), the power data in the time domainto a power threshold.

At operation 1108, the process flow 1100 can comprise based on a resultof the power data being compared to the power threshold, sorting, by thesystem (e.g., analysis component 218), the power data into bins at astorage component.

At operation 1110, the process flow 1100 can comprise analyzing, by thesystem, the power data in the time domain that is sorted according to apower threshold

At operation 1112, the process flow 1100 can comprise counting, by thesystem (e.g., accumulator and/or counting circuit 220), respectivequantities of power data values at respective bins of the group of bins.

At operation 1114, the process flow 1100 can comprise aligning, by thesystem (e.g., measurement component 214 and/or processor 207), differentsets of the power data in the time domain to one another based onrespective different time ranges of the time domain in which therespective sets of power data were read in connection with theanalyzing.

At operation 1116, the process flow 1100 can comprise enhancing, by thesystem (e.g., measurement circuit 214 and/or processor 207), accuracy ofthe power data in the time domain that is detected by using, by thesystem, information from the control-plane of the radio system.

At operation 1118, the process flow 1100 can comprise triggering, by thesystem (e.g., read circuit 211 and/or accumulator or counting circuit220), a copying of or transferring of the power data from at least oneof the group of bins, based on a counter threshold of a specified countof power values binned being reached or exceeded.

At operation 1120, the process flow 1100 can comprise triggering, by thesystem, based on a power value threshold being met or exceeded, aninterrupt flag to trigger a system modification event in response to thetriggering of the interrupt flag.

At operation 1124, the process flow 1100 can comprise storing, by thesystem (e.g., memory 209 and/or read circuit 211), the power data in thetime domain at a memory or other storage.

For simplicity of explanation, the computer-implemented methodologiesand/or processes provided herein are depicted and/or described as aseries of acts. The subject innovation is not limited by the actsillustrated and/or by the order of acts, for example acts can occur inone or more orders and/or concurrently, and with other acts notpresented and described herein. The operations of process flows ofdiagrams 1100 are example operations, and there can be one or moreembodiments that implement more or fewer operations than are depicted.

Furthermore, not all illustrated acts can be utilized to implement thecomputer-implemented methodologies in accordance with the describedsubject matter. In addition, the computer-implemented methodologiescould alternatively be represented as a series of interrelated statesvia a state diagram or events. Additionally, the computer-implementedmethodologies described hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring the computer-implemented methodologies tocomputers. The term article of manufacture, as used herein, is intendedto encompass a computer program accessible from any machine-readabledevice or storage media.

In summary, technology described herein can gather and statisticallyanalyze time domain power data for enabling real-time adjustment of oneor more parameters of a radio system. In an embodiment, a system cancomprise a processor and a read circuit communicatively coupled to theprocessor, wherein the processor controls the read circuit to read powerdata in a time domain from a radio system, and an analysis componentcommunicatively coupled to the processor, wherein the analysis componentcompares the power data in the time domain to a power threshold, andwherein, based on a result of the power data being compared to the powerthreshold, the analysis component sorts the power data into bins at astorage component communicatively coupled to the processor.

As a result, a method can be provided to read, collect, statisticallyanalyze and/or store power data information for immediate and/or lateranalysis. One or more actions can be taken relative to the power data,to assist with radio system frequency, maintenance, customer experienceand/or the like. In one or more embodiments, one or more actions can betriggered, such as relative to a quantity, quality and/or other aspectof the data read, collected and/or stored. A practical application ofone or more techniques performed by one or more embodiments describedherein can be collection of datas being time-aligned to one anotherrelative to various tap point (data collection points) of a radiosystem.

Another practical application can be collecting statistics of currenttraffic of DL and UL on the RU side instead of the DU side of arespective radio system, such as where time domain data is native (e.g.,on the DL/UL side). In this way, information can be gathered “upfront”to allow for any parameter adjustment. Such practical application cancomprise the gather and collecting of TD power data, and thus thebuilding of TD power data statistics over time. Furthermore, in view ofstatistical analysis performed, one or more triggers can be implemented,such as for review and/or for automatic conditioning, modification,adjustment and/or the like of one or more aspects, parameters and/orcharacteristics of a respective radio system.

Such comparable data can be beneficial for a variety of applications, asdescribed herein. For example, radio systems typically employ largequantities of power, and the one or more embodiments described hereincan, through data collection and storage, facilitate reducing powerconsumption of a respective radio system. This can be facilitatedthrough performance enhancements, firmware changes and/or upgrades,and/or over the air updates to customer equipment in the field (e.g.,which are employing and/or can employ the respective radio system).Particular advantages can comprise, but are not limited to, reduction ofoccurrence/rate of no fault found (NFF) returns, cost of field returns,and/or customer outage occurrences/times.

The systems and/or devices have been (and/or will be further) describedherein with respect to interaction between one or more components. Suchsystems and/or components can include those components or sub-componentsspecified therein, one or more of the specified components and/orsub-components, and/or additional components. Sub-components can beimplemented as components communicatively coupled to other componentsrather than included within parent components. One or more componentsand/or sub-components can be combined into a single component providingaggregate functionality. The components can interact with one or moreother components not specifically described herein for the sake ofbrevity, but known by those of skill in the art.

One or more embodiments described herein are inherently and/orinextricably tied to computer technology and cannot be implementedoutside of a computing environment. For example, one or more processesperformed by one or more embodiments described herein can moreefficiently, and even more feasibly, provide data collection, such astime-aligned data collection in the time domain, as compared to existingsystems and/or techniques. Systems, computer-implemented methods and/orcomputer program products facilitating performance of these processesare of great utility in the field of data storage and/or radio systemmanagement and cannot be equally practicably implemented in a sensibleway outside of a computing environment.

One or more embodiments described herein can employ hardware and/orsoftware to solve problems that are highly technical, that are notabstract, and that cannot be performed as a set of mental acts by ahuman. For example, a human, or even thousands of humans, cannotefficiently, accurately and/or effectively collect and statisticallyanalyze time domain data from a DFE chain in the time that one or moreembodiments described herein can facilitate this process. And, neithercan the human mind nor a human with pen and paper electronically collectand statistically analyze time domain data from a DFE chain as conductedby one or more embodiments described herein.

In one or more embodiments, one or more of the processes describedherein can be performed by one or more specialized computers (e.g., aspecialized processing unit, a specialized classical computer, and/oranother type of specialized computer) to execute defined tasks relatedto the one or more technologies describe above. One or more embodimentsdescribed herein and/or components thereof can be employed to solve newproblems that arise through advancements in technologies mentionedabove, employment of cloud computing systems, computer architectureand/or another technology.

One or more embodiments described herein can be fully operationaltowards performing one or more other functions (e.g., fully powered on,fully executed and/or another function) while also performing the one ormore operations described herein.

Example Operating Environment

FIG. 12 is a schematic block diagram of an operating environment 1200with which the described subject matter can interact. The system 1200comprises one or more remote component(s) 1210. The remote component(s)1210 can be hardware and/or software (e.g., threads, processes,computing devices). In some embodiments, remote component(s) 1210 can bea distributed computer system, connected to a local automatic scalingcomponent and/or programs that use the resources of a distributedcomputer system, via communication framework 1240. Communicationframework 1240 can comprise wired network devices, wireless networkdevices, mobile devices, wearable devices, radio access network devices,gateway devices, femtocell devices, servers, etc.

The system 1200 also comprises one or more local component(s) 1220. Thelocal component(s) 1220 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)1220 can comprise an automatic scaling component and/or programs thatcommunicate/use the remote resources 1210 and 1220, etc., connected to aremotely located distributed computing system via communicationframework 1240.

One possible communication between a remote component(s) 1210 and alocal component(s) 1220 can be in the form of a data packet adapted tobe transmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 1210 and a localcomponent(s) 1220 can be in the form of circuit-switched data adapted tobe transmitted between two or more computer processes in radio timeslots. The system 1200 comprises a communication framework 1240 that canbe employed to facilitate communications between the remote component(s)1210 and the local component(s) 1220, and can comprise an air interface,e.g., interface of a UMTS network, via a long-term evolution (LTE)network, etc. Remote component(s) 1210 can be operably connected to oneor more remote data store(s) 1250, such as a hard drive, solid statedrive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 1210 side of communicationframework 1240. Similarly, local component(s) 1220 can be operablyconnected to one or more local data store(s) 1230, that can be employedto store information on the local component(s) 1220 side ofcommunication framework 1240.

Example Computing Environment

In order to provide additional context for various embodiments describedherein, FIG. 13 and the following discussion are intended to provide abrief, general description of a suitable computing environment 1300 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, the methods can be practiced with othercomputer system configurations, including single-processor ormultiprocessor computer systems, minicomputers, mainframe computers,Internet of Things (IoT) devices, distributed computing systems, as wellas personal computers, hand-held computing devices, microprocessor-basedor programmable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, exclude only propagating transitory signals perse as modifiers and do not relinquish rights to all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

Referring still to FIG. 13 , the example computing environment 1300which can implement one or more embodiments described herein includes acomputer 1302, the computer 1302 including a processing unit 1304, asystem memory 1306 and a system bus 1308. The system bus 1308 couplessystem components including, but not limited to, the system memory 1306to the processing unit 1304. The processing unit 1304 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures can also be employed as theprocessing unit 1304.

The system bus 1308 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1306includes ROM 1310 and RAM 1312. A basic input/output system (BIOS) canbe stored in a nonvolatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1302, such as during startup. The RAM 1312 can also include a high-speedRAM such as static RAM for caching data.

The computer 1302 further includes an internal hard disk drive (HDD)1314 (e.g., EIDE, SATA), and can include one or more external storagedevices 1316 (e.g., a magnetic floppy disk drive (FDD) 1316, a memorystick or flash drive reader, a memory card reader, etc.). While theinternal HDD 1314 is illustrated as located within the computer 1302,the internal HDD 1314 can also be configured for external use in asuitable chassis (not shown). Additionally, while not shown inenvironment 1300, a solid state drive (SSD) could be used in additionto, or in place of, an HDD 1314.

Other internal or external storage can include at least one otherstorage device 1320 with storage media 1322 (e.g., a solid state storagedevice, a nonvolatile memory device, and/or an optical disk drive thatcan read or write from removable media such as a CD-ROM disc, a DVD, aBD, etc.). The external storage 1316 can be facilitated by a networkvirtual machine. The HDD 1314, external storage device(s) 1316 andstorage device (e.g., drive) 1320 can be connected to the system bus1308 by an HDD interface 1324, an external storage interface 1326 and adrive interface 1328, respectively.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1302, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, other types ofstorage media which are readable by a computer, whether presentlyexisting or developed in the future, could also be used in the exampleoperating environment, and further, that any such storage media cancontain computer-executable instructions for performing the methodsdescribed herein.

A number of program modules can be stored in the drives and RAM 1312,including an operating system 1330, one or more application programs1332, other program modules 1334 and program data 1336. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1312. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1302 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1330, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 13 . In such an embodiment, operating system 1330 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1302.Furthermore, operating system 1330 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1332. Runtime environments are consistent executionenvironments that allow applications 1332 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1330can support containers, and applications 1332 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1302 can be enabled with a security module, such as atrusted processing module (TPM). For instance, with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1302, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1302 throughone or more wired/wireless input devices, e.g., a keyboard 1338, a touchscreen 1340, and a pointing device, such as a mouse 1342. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1304 through an input deviceinterface 1344 that can be coupled to the system bus 1308, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1346 or other type of display device can be also connected tothe system bus 1308 via an interface, such as a video adapter 1348. Inaddition to the monitor 1346, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1302 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1350. The remotecomputer(s) 1350 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1302, although, for purposes of brevity, only a memory/storage device1352 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1354 and/orlarger networks, e.g., a wide area network (WAN) 1356. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1302 can beconnected to the local network 1354 through a wired and/or wirelesscommunication network interface or adapter 1358. The adapter 1358 canfacilitate wired or wireless communication to the LAN 1354, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1358 in a wireless mode.

When used in a WAN networking environment, the computer 1302 can includea modem 1360 or can be connected to a communications server on the WAN1356 via other means for establishing communications over the WAN 1356,such as by way of the Internet. The modem 1360, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1308 via the input device interface 1344. In a networkedenvironment, program modules depicted relative to the computer 1302 orportions thereof, can be stored in the remote memory/storage device1352. The network connections shown are example and other means ofestablishing a communications link between the computers can be used.

When used in either a LAN or WAN networking environment, the computer1302 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1316 asdescribed above. Generally, a connection between the computer 1302 and acloud storage system can be established over a LAN 1354 or WAN 1356e.g., by the adapter 1358 or modem 1360, respectively. Upon connectingthe computer 1302 to an associated cloud storage system, the externalstorage interface 1326 can, with the aid of the adapter 1358 and/ormodem 1360, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1326 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1302.

The computer 1302 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

Conclusion

The above description of illustrated embodiments of the one or moreembodiments described herein, comprising what is described in theAbstract, is not intended to be exhaustive or to limit the describedembodiments to the precise forms described. While one or more specificembodiments and examples are described herein for illustrative purposes,various modifications are possible that are considered within the scopeof such embodiments and examples, as those skilled in the relevant artcan recognize.

In this regard, while the described subject matter has been described inconnection with various embodiments and corresponding figures, whereapplicable, other similar embodiments can be used or modifications andadditions can be made to the described embodiments for performing thesame, similar, alternative, or substitute function of the describedsubject matter without deviating therefrom. Therefore, the describedsubject matter should not be limited to any single embodiment describedherein, but rather should be construed in breadth and scope inaccordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures to optimize space usage or enhanceperformance of user equipment. A processor can also be implemented as acombination of computing processing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or a firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances.

While the embodiments are susceptible to various modifications andalternative constructions, certain illustrated implementations thereofare shown in the drawings and have been described above in detail.However, there is no intention to limit the various embodiments to theone or more specific forms described, but on the contrary, the intentionis to cover all modifications, alternative constructions, andequivalents falling within the spirit and scope.

In addition to the various implementations described herein, othersimilar implementations can be used or modifications and additions canbe made to the described implementation(s) for performing the same orequivalent function of the corresponding implementation(s) withoutdeviating therefrom. Still further, multiple processing chips ormultiple devices can share the performance of one or more functionsdescribed herein, and similarly, storage can be effected across aplurality of devices. Accordingly, the various embodiments are not to belimited to any single implementation, but rather are to be construed inbreadth, spirit and scope in accordance with the appended claims.

What is claimed is:
 1. A system, comprising: a processor and a readcircuit communicatively coupled to the processor, wherein the processorcontrols the read circuit to read power data in a time domain from aradio system; and an analysis component communicatively coupled to theprocessor, wherein the analysis component compares the power data in thetime domain to a power threshold, and wherein, based on a result of thepower data being compared to the power threshold, the analysis componentsorts the power data into bins at a storage component communicativelycoupled to the processor.
 2. The system of claim 1, wherein the readcircuit reads the power data in the time domain along a selected timerange of the time domain that is defined by time boundaries of the radiosystem.
 3. The system of claim 1, wherein the read circuit reads thepower data at a defined granularity based on a period of one symbol oftime of the time domain.
 4. The system of claim 1, wherein the powerthreshold is applied to separate the power data into root-mean-squarevalues or peak values.
 5. The system of claim 1, wherein the readcircuit transmits the power data in the time domain along the uplinkchain or another uplink chain of the radio system other than the uplinkchain, and wherein the memory receives the power data in the timedomain.
 6. The system of claim 1, further comprising: an accumulatorcircuit or counter circuit communicatively coupled to the processor,wherein the accumulator circuit or counter circuit records power dataquantities stored at one or more of the bins at the storage component.7. The system of claim 6, wherein the accumulator circuit or the countercircuit generates an interrupt signal triggering a copying ortransferring of the power data from one or more of the bins at thestorage component.
 8. The system of claim 1, wherein the power data inthe time domain is first power data, and further comprising: a delayingcircuit communicatively coupled to the processor that delays secondpower data in the time domain to thereby adjust a selected time range ofthe second power data to the selected time range of the first powerdata, and wherein the read circuit synchronously reads the power dataand the second power data.
 9. The system of claim 1, wherein theanalysis component compares the power data in the time domain prior tostorage of the power data in the time domain at the storage component.10. The system of claim 1, wherein the analysis component compares thepower data in the time domain after an initial recording of the powerdata in the time domain to the storage component.
 11. The system ofclaim 1, wherein the system is part of a master system, comprising:systems comprising the system, wherein respective systems of the systemsare configured to read and record into respective bins at the storagecomponent, respective power data in the time domain from respective tappoints along an uplink path or a downlink path of the radio system.